home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 4
/
QRZ Ham Radio Callsign Database - Volume 4.iso
/
digests
/
tcp
/
940173.txt
< prev
next >
Wrap
Internet Message Format
|
1994-11-13
|
13KB
Date: Mon, 15 Aug 94 04:30:02 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V94 #173
To: tcp-group-digest
TCP-Group Digest Mon, 15 Aug 94 Volume 94 : Issue 173
Today's Topics:
dama_slave problem or not.?
DAMA Specification
dial on jnos110f (2 msgs)
Linux and AX.25
SLIP Help and PPP Question
wnos-940815.zip uploaded
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Mon, 15 Aug 94 09:02:11 EST
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: dama_slave problem or not.?
To: TCP-GROUP <TCP-GROUP@ucsd.edu>, wnos-group <WNOS-L@edugraf.ufsc.br>
Also calling for Phil Karn ka9q advice on this please.!
My local dama digi sysops tell me that the trace below is not correct
and that instead of flushing out my ax25_queue to the TX on the first sign
of a ax25 L2 connect I should Hold off and wait for one poll
IE: wait for a RR(P) dama frame. i have looked at the way ALL tcpip nos
version work and we all get the tcp data out in responce to a UA
we never wait for the next poll frame RR do we ?? or should WE ?? makes things
very slow to start.
as far as i know the rules for dama say i cant transmit unless im polled with
a dama bit set from the dama_master.
the trace below shows the dama_master sending me a frame I am alloud to TX
a responce, and i also send data in the same transmit key up
IS THIS wrong ???
Need Urgent advice.
Thanks. Barry. dc0hk/gm8sau
NB. (DAMA) = dama_master comes from the digi.
I
I
uhf sent (Sun Aug 14 09:41:33 1994): I
AX25: DC0HK to DB0RT-10 via DB0DAR SABM(P) I
uhf recv (Sun Aug 14 09:41:34 1994): I
uhf recv (Sun Aug 14 09:41:41 1994): v
AX25: DB0RT-10 to DC0HK via DB0DAR* UA(F) ªDAMAß
uhf sent (Sun Aug 14 09:41:41 1994):
AX25: DC0HK to DB0RT-10 via DB0DAR I NR=0 NS=0 pid=IP
IP: len 84 44.130.24.71->44.130.60.100 ihl 20 ttl 63 prot ICMP
ICMP: type Echo Request id 63232 seq 0
.............. !"#$%&'()*+,-./01234567
------------------------------
Date: Mon, 15 Aug 94 10:02:46 EST
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: DAMA Specification
To: kurpiers@rbg.informatik.th-darmstadt.de, TCP-GROUP <TCP-GROUP@ucsd.edu>,
Hello Alex
I understand you have access to the actual current dama spectification
Can you please mail it to me or to one of the discussion groups.
Thanks. Barry.
btitmars@esoc.bitnet.
------------------------------
Date: Sun, 14 Aug 1994 12:26:35 -0600 (MDT)
From: LARSEN KARL AMSRL-SL-EC 505-678-3145 <klarsen@arl.army.mil>
Subject: dial on jnos110f
To: TCP Digest <tcp-group@ucsd.edu>
Hi guys, my work internet system has installed a telephone
dial-up system that allows me to log on with my hostname and password and
after sending slip, I'm connected to the internet! I have done this with
net.exe from Phil Karn but find that the dialer part of jnos110f changes
the " which I put in the dialer script to < ?????? > which my modem
cannot read and do it's work.
Has anyone else tried the later versions of jnos with the dialer function?
I sure want to be able to do this with newer nos but at the time I am
stumped.
Thanks, de karl k5di
------------------------------
Date: Sun, 14 Aug 1994 20:02:34 +0100
From: "Brian A. Lantz" <brian@lantz.cftnet.com>
Subject: dial on jnos110f
To: LARSEN KARL AMSRL-SL-EC 505-678-3145 <klarsen@arl.army.mil>
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--2107838718-34705169-776908954:#1561
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Sun, 14 Aug 1994, LARSEN KARL AMSRL-SL-EC 505-678-3145 wrote:
> Has anyone else tried the later versions of jnos with the dialer function?
> I sure want to be able to do this with newer nos but at the time I am
> stumped.
>
Here is a TNOS dialer file (direct desendent for JNOS). The names were
changed to protect the innocent. ;-)
-----------------------------------------------------------
Brian A. Lantz/KO4KS brian@lantz.cftnet.com
REAL PORTION of Microsoft Windows code:
while (memory_available) {
eat_major_portion_of_memory (no_real_reason);
if (feel_like_it)
make_user_THINK (this_is_an_OS);
gates_bank_balance++;
}
--2107838718-34705169-776908954:#1561
Content-Type: TEXT/PLAIN; charset=US-ASCII; name="/dialup"
Content-Transfer-Encoding: BASE64
Content-ID: <Pine.3.89.9408142034.D1561@lantz.cftnet.com>
Content-Description: Sample dialer script
Y29udHJvbCBkb3duDQp3YWl0IDIwMDANCmNvbnRyb2wgdXANCnNwZWVkIDk2
MDANCnNlbmQgImF0elxyYXRtMGwwXHIiDQp3YWl0IDEwMDANCnNlbmQgImF0
ZHRkNTU1LTU1NTVcciINCndhaXQgNDUwMDAgIkNPTk5FQ1QiDQp3YWl0IDE1
MDAwICJvZ2luIg0Kd2FpdCAxMDAwDQpzZW5kICJteW5hbWVcciINCndhaXQg
NTAwMCAiYXNzd29yZCINCndhaXQgMTAwMA0Kc2VuZCAibXlwYXNzd29yZFxy
Ig0Kd2FpdCAxMjAwMDANCg==
--2107838718-34705169-776908954:#1561--
------------------------------
Date: Sun, 14 Aug 94 22:26:30 PDT
From: srbible@cs.nps.navy.mil (Steven R. Bible)
Subject: Linux and AX.25
To: tcp-group@ucsd.edu
Well, having set aside this weekend to compile and get running Alan's AX.25
code in the Linux kernel I have succeeded. It is really neat to see two
computers telnet and ftp together in a native sort of way :-).
I did run into a few minor problems that I hope can be cleared up. Some of
these things are errata that I found and some are just plain unexplainable
problems I ran into. Could interested readers verify these just incase I am
mistaken.
I used:
- linux-1.1.43 kernel with patch 44
- ax25krnl.tgz and ax25util.tgz from the directory AX25022
- patches to ax25krnl 23 and 24
- (I did not download and include net-tools-1.1.38.tar.gz
I discovered this later; should I compile it in or is
it already in the kernel 1.1.43? )
- two DRSI DPK-9600 in KISS mode
- two TEKK KS-900 radios (441.050 MHz at 2 watts)
- two computers, one a 386DX-33 and the other a 486DX-66
Some errata to Terry Dawson's NET-2/3 HOWTO.
1. p.53 - krnl022.tgz should read ax25krnl.tgz
- user022.tgz should read ax25util.tgz
- need to add a section explaining how to apply patches to
the ax25 kernel code.
2. p.54 - the example # gzip -dc user022.tgz | tar xvvof -
is this right? ^^^^^ (?xvf?)
3. p.12 - /pub/misc/Linux/Networking/... should read
/pub/Linux/Networking/... (two places)
Other problems:
3. When unpacking the user programs and 'make install' it gets down
to a point where it fails. The following is printed out:
install -m 755 -s -o bin -g bin axarp /usr/local/ax25/etc
install: axarp: No such file or directory
make: *** [install] Error 1
I looked and axarp is in /usr/local/ax25/etc.
4. In the end I suspect that the executables for the user programs
were to end up in /usr/local/ax25/bin but they were in
/usr/local/ax25/src. I copied them over. Did this happen
because 'make install' did not complete?
General questions:
5. Is the PI2 code already included in the ax25krnl? I think the
answer is yes, however the dates of the pi.c, etc. in the
ax25krnl sources was older than the pi.c code from
pi2-0.6ALPHA.tgz from hydra.carleton.ca.
6. What now? Now I need to learn about how to configure this whole
mess. I need to learn more about routing and such. I type in
the 'ifconfig' line and the 'route add' but I don't understand
what they are doing (I am not a sys admin type). I want to be
able to configure my ethernet card and the TNC. I would like to
set up a Linux machine on the air for others to telent, ftp, and
get mail from and have it connected to the school's ethernet
and ultimately the internet to get news and mail. I need to
investigate JNOS for Linux too.
7. I did try Linux+AX25 on the local 2 meter frequency using a
PACCOMM TNC-200 in KISS mode. I was able to 'call' and 'ftp'
to the local MSYS BBS which is setup for TCP/IP. But when I
tried to telnet, MSYS would ask for my callsign, I typed it in
and MSYS simply disconnected me. I can telnet to the MSYS BBS
using JNOS, proving to me that the BBS end is working (?).
I'm wondering what Linux+AX25 is doing to cause this?
That's about it. I took me two full days to read all of the docs, figure
out what was needed, what was to be done, and lots of trial and error.
Is there a need for a HOWTO to set all of this up (Alan mentioned this in
AX25017/INSTALL.TXT)? The NET-2 HOWTO guide gives a good overview of what
needs to be done, but my biggest problem was figuring out what was the
latest code, code versions that required other versions, etc. I first
gathered up all the HOWTOs, READMEs, man pages, etc. and correlated all the
information. Not all of it matched. I downloaded and used the latest code
I code find (see above).
An Amateur Radio HOWTO would be a big help in outlining the steps to get
Linux+AX25 up and running. I think what would be more important is how to
config all of it together to make a useful system or LAN. I do not
understand routing, but I am reading Olaf Kirch's Network Administrator's
Guide. A HOWTO explaining how to set up an amateur lan with linux and JNOS
boxes would be a better approach for the average ham who does not have
networking and routing experience.
I have ordered two Ottawa PI2 cards. As soon as those arrive I will be
integrating them into the system.
Terry has also compiled a listing of Linux amateur radio software, what and
where to get it. Look for it on comp.os.linux.announce.
73,
Steve, N7HPR
srbible@cs.nps.navy.mil
Naval Postgraduate School, Monterey, CA 93943
------------------------------
Date: Sun, 14 Aug 94 18:46:48 CST
From: kf5mg@metronet.com
Subject: SLIP Help and PPP Question
To: tcp-group mailling list <tcp-group@ucsd.edu>
Greetings all...
I'd like to get either SLIP or PPP going with JNOS. Can someone send
me a dialer script that might help me get started? Also... my SLIP provider
assigns me a IP Address at connect time. Most of the SLIP software I've
seen lets you parse the IP Address for the session and assign that IP
address to the SLIP port. Can you do that with JNOS?
On the subject of PPP. What advantages does PPP have over SLIP? In both
cases, my SLIP/PPP provider assigns dynamic IP addresses. BOOTP is not an
option.
Finally... once I get SLIP ( or PPP ) going and I figure out how to
handle the dynamic IP Address, I need to figure out how to get a remote,
JNOS gateway to update and ENCAP route to my system using the current
IP address. If anyone has got that worked out, please let me know. A
non-automatic solution would be to telnet to the remote JNOS box and add
the encap route manually each time the SLIP connection is made, but I'd
like to find some sort of automatic method.
73's de Jack - kf5mg
Internet - kf5mg@kf5mg.ampr.org - 44.28.0.14
- kf5mg@metronet.com - work (looking for)
AX25net - kf5mg@kf5mg.#dfw.tx.usa.noam - home (817) 488-4386
------------------------------
Date: Mon, 15 Aug 94 08:50:23 EST
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: wnos-940815.zip uploaded
To: TCP-GROUP <TCP-GROUP@ucsd.edu>, wnos-group <WNOS-L@EDUGRAF.UFSC.BR>
Ok i am about to upload to ftp.ucsd.edu:incoming
file wnos-940815.zip this is the version with the dama_slave build in.
its not completely finished, there are 2 known bugs with the dama
one bug is in despute as per the actual implementation of dama
and the sending of I frames on recipt of a UA(dama)
the other is if both ends of the network link are dama nodes then the
VC is never shutdown when the tcp layer is finished. like the T3Disc
function. due to cont polling by the dama digis the T3 time is always reset
I will post the code I NEED help to fix this one.
Help me Ill help you to get a new wnos. Ok.
Barry.
------------------------------
End of TCP-Group Digest V94 #173
******************************